This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
deps: upgrade npm to 2.7.1 #9408
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@othiym23 Moving to the 0.12.2 milestone because the current plan is to have v0.12.1 be v0.12.0 + the OpenSSL upgrade. Node v0.12.1 would thus ship with npm 2.5.1. I know it's different than our initial idea and what we talked about in #libuv. Do you have any objections to that? |
|
If it gets a patched 0.12.1 out faster, I have no objections, although I think the risk of including the upgraded npm is very low. |
|
Thank you for your input @othiym23! |
|
Closing in favor of #9443. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[email protected]is a pretty hefty release. I've included the four most significant changes below, and there are many others in the fullCHANGELOG.md.6823807#7121
npm install --savefor Gitdependencies saves the URL passed in, instead of the temporary directory used
to clone the remote repo. Fixes using Git dependencies when shrinkwwapping.
In the process, rewrote the Git dependency caching code. Again. No more
single-letter variable names, and a much clearer workflow.
(@othiym23)
abdd040[email protected]: Provide more helpful error messages when JSONparse errors are encountered by using a more forgiving JSON parser than
JSON.parse. (@smikes)
c56cfcd#7525
npm dedupehandles scopedpackages. (@KidkArolis)
4ef1412#7075 If you try to tag a release
as a valid semver range,
npm publishandnpm tagwill error early insteadof proceeding. (@smikes)